Apparatus for coupling to existing power lines

ABSTRACT

Methods, systems, and apparatus for monitoring and controlling electronic devices using wired and wireless protocols are disclosed. The systems and apparatus may monitor their environment for signals from electronic devices. The systems and apparatus may take and disambiguate the signals that are received from the devices in their environment to identify the devices and associate control signals with the devices. The systems and apparatus may use communication means to send control signals to the identified electronic devices. Multiple apparatuses or systems may be connected together into networks, including mesh networks, to make for a more robust architecture.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 16/588,378 titled “METHODS, SYSTEMS, AND APPARATUS FOR THEMONITORING, CONTROLLING, AND COMMUNICATING OF ELECTRONIC DEVICES toBogdanovich, filed Sep. 30, 2019, which is a continuation of U.S. patentapplication Ser. No. 15/783,833 titled “METHODS, SYSTEMS, AND APPARATUSFOR THE MONITORING, CONTROLLING, AND COMMUNICATING OF ELECTRONICDEVICES” to Bogdanovich, filed Oct. 13, 2017 (now U.S. Pat. No.10,432,257), which is a continuation of U.S. patent application Ser. No.15/404,174 titled “METHODS, SYSTEMS, AND APPARATUS FOR THE MONITORING,CONTROLLING, AND COMMUNICATING OF ELECTRONIC DEVICES” to Bogdanovich,filed Jan. 11, 2017 (now U.S. Pat. No. 9,793,952), which is acontinuation-in-part of U.S. patent application Ser. No. 14/806,531titled “METHODS, SYSTEMS, AND APPARATUS FOR THE MONITORING, CONTROLLING,AND COMMUNICATING OF LIGHTING SYSTEMS” to Bogdanovich, filed Jul. 22,2015, which claims priority to U.S. Provisional Patent Application No.62/027,627 to Bogdanovich, titled “COMMUNICATION CUBE METHOD ANDSYSTEM”, filed Jul. 22, 2014 and U.S. Provisional Patent Application No.62/027,626 to Bogdanovich, titled “HALL-EFFECT ELECTRIC POWER MONITOR”,filed Jul. 22, 2014, all of which are incorporated by reference in theirentireties.

This application incorporates by reference U.S. patent application Ser.No. 14/806,511 filed Jul. 22, 2015 in its entirety.

BACKGROUND

The invention relates generally to the field of monitoring, controlling,and communicating of devices. More particularly, the invention relatesto a radio communication to power line communication bridge andnetworking system for the monitoring, controlling, and communicating ofdevices such as lighting systems.

SUMMARY

In one respect, disclosed may be a method for monitoring, controlling,and communicating. The method may comprise: splicing at least onecontrol clamp to the power lines of at least one device; establishing apowernet control unit (PCU) power line communication link between atleast one powernet control unit; connecting at least one of the at leastone powernet control unit to a communication gateway in order to enablecommunication with the powernet control unit from a mobile device, alocal server, and/or a remote server using a powernet controlunit/communication cube (PCU/CC) dashboard application; using a PCUinter-PCU/CC wireless module and a communication cube (CC) inter-PCU/CCwireless module to communicate between the at least one powernet controlunit and at least one communication cubes; using CC inter-PCU/CCwireless modules to communicate between the at least one communicationcube; using the PCU power line communication link to communicate withthe at least one powernet control unit; using the at least onecommunication cube with the spliced at least one control clamp tomonitor and control the at least one device; using RFID modules andBluetooth modules of the at least one communication cube to create atleast one RFID/Bluetooth beacon; and using at least one monitor sensorof the at least one communication cube to monitor the area around the atleast one device.

In another respect, disclosed is a method for monitoring, controlling,and communicating. The method may comprise: splicing at least onecontrol clamp to the power lines of at least one device; establishing apower line communication link between at least one powernet controlcommunication cube; connecting at least one of the at least one powernetcontrol communication cube to a communication gateway in order to enablecommunication with the at least one powernet control communication cubefrom at least one of a mobile device and a remote server using apowernet control communication cube (PCCC) dashboard application; usinga communication port of the at least one powernet control communicationcube to communicate between the at least one powernet controlcommunication cube; using the power line communication link tocommunicate between the at least one powernet control communicationcube; using the at least one powernet control communication cube withthe spliced at least one control clamp to monitor and control the atleast one device; using RFID modules and Bluetooth modules of the atleast one powernet control communication cube to create at least oneRFID/Bluetooth beacon; and using at least one monitor sensor of the atleast one powernet control communication cube to monitor the area aroundthe at least one device.

In one respect, disclosed is an apparatus for monitoring, controlling,and communicating. The apparatus may comprise: at least one powernetcontrol unit, wherein the power control unit (PCU) may comprise: a PCUhousing; a PCU system bus within the PCU housing; at least one PCUprocessor coupled to the PCU system bus; PCU system memory coupled tothe at least one PCU processor; at least one PCU non-transitory memoryunit coupled to the at least one PCU processor; a GPS module coupled tothe PCU system bus; a power port coupled to the PCU system bus; a PCUinternal battery coupled to the PCU system bus; a communication portcoupled to the PCU system bus, wherein the communication port maycomprise at least one of: Wi-Fi, Ethernet, and a cellular network radio;a PCU inter-PCU/CC wireless module coupled to the PCU system bus,wherein the PCU inter-PCU/CC wireless module may comprise at least oneof: Bluetooth, 6LoWPan, and ZigBee; and PCU code stored on the at leastone PCU non-transitory memory unit; a communication gateway coupled tothe communication port, wherein the communication gateway may beconnected to a cloud; at least one of a local server and a mobile deviceconnected to the communication gateway and configured to communicatewith the PCU through the communication gateway; at least one of a remoteserver and a mobile device connected to the cloud and configured tocommunicate with the PCU through the communication gateway; and at leastone communication cube, wherein the communication cube (CC) maycomprise: a CC housing; a CC system bus within the communication cube CChousing; at least one CC processor coupled to the CC system bus; CCsystem memory coupled to the at least one CC processor; at least one CCnon-transitory memory unit coupled to the at least one CC processor; anRFID module coupled to the CC system bus; a Bluetooth module coupled tothe CC system bus; a CC internal battery coupled to the CC system bus; aCC inter-PCU/CC wireless module coupled to the CC system bus, whereinthe CC inter-PCU/CC wireless module may comprise at least one of:Bluetooth, 6LoWPan, and ZigBee; at least one control port coupled to theCC system bus; at least one control clamp coupled to the at least onecontrol port; at least one monitor sensor coupled to the CC system bus;and CC code stored on the at least one CC non-transitory memory unit;wherein the PCU code when executed by the at least one PCU processorsmay be configured to perform a PCU method that may comprise:establishing a PCU power line communication link between the at leastone powernet control unit; communicating with the at least one powernetcontrol unit through the PCU power line communication link;communicating with the at least one communication cube through the PCUinter-PCU/CC wireless module and the CC inter-PCU/CC wireless module;and communicating with a PCU/CC dashboard application; and wherein theCC code when executed by the at least one CC processor may be configuredto perform a CC method that may comprise: communicating with the atleast one powernet control unit through the PCU inter-PCU/CC wirelessmodule and the CC inter-PCU/CC wireless module; communicating with theat least one communication cube through the CC inter-PCU/CC wirelessmodule; monitoring and controlling at least one device through the atleast one control clamp, wherein the at least one device may comprise alighting system; creating an RFID/Bluetooth beacon; and monitoring theat least one monitor sensor.

In another respect, disclosed may be an apparatus for monitoring,controlling, and communicating. The apparatus may comprise: at least onepowernet control communication cube, wherein the powernet controlcommunication cube (PCCC) may comprise: a housing; a system bus withinthe housing; at least one processor coupled to the system bus; systemmemory coupled to the at least one processor; at least onenon-transitory memory unit coupled to the at least one processor; a GPSmodule coupled to the system bus; a power port coupled to the systembus; an internal battery coupled to the system bus; a communication portcoupled to the system bus, wherein the communication port may compriseat least one of: Wi-Fi, PLC, Ethernet, ZigBee, 6LoWPan, and Bluetooth;at least one control port coupled to the system bus; at least onecontrol clamp coupled to the at least one control port; at least onemonitor sensor coupled to the system bus; and PCCC code stored on the atleast one non-transitory memory unit; a communication gateway coupled tothe communication port, wherein the communication gateway may beconnected to a cloud; at least one of a local server and a mobile deviceconnected to the communication gateway and configured to communicatewith the PCCC through the communication gateway; and at least one of aremote server and a mobile device connected to the cloud and configuredto communicate with the PCCC through the communication gateway; whereinthe PCCC code when executed by the at least one processor may beconfigured to perform a PCCC method that may comprise: establishing apower line communication link between the at least one powernet controlcommunication cube; communicating with a PCCC dashboard application;communicating with the at least one powernet control communication cubethrough the power line communication link; communicating with the atleast one powernet control communication cube through the communicationport; monitoring and controlling at least one device through the atleast one control clamp, wherein the at least one device may comprise alighting system; creating an RFID/Bluetooth beacon; and monitoring theat least one monitor sensor.

Numerous additional embodiments may also be possible.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects and advantages of the invention may become apparent uponreading the detailed description and upon reference to the accompanyingdrawings.

FIG. 1 is a block diagram illustrating an apparatus for monitoring,controlling, and communicating in accordance with embodiments.

FIG. 2 is a block diagram illustrating an apparatus for monitoring,controlling, and communicating in accordance with embodiments.

FIG. 3 is a block diagram illustrating an apparatus for monitoring,controlling, and communicating in accordance with embodiments.

FIG. 4 is a block diagram illustrating a method for monitoring,controlling, and communicating of devices in accordance withembodiments.

FIG. 5 is a block diagram illustrating a method for monitoring,controlling, and communicating of devices in accordance withembodiments.

FIG. 6 illustrates a method for communicating with, identifying,monitoring and controlling electronic devices connected to a circuit, inan embodiment.

FIG. 7 illustrates a method for communicating with, identifying,monitoring and controlling electronic devices connected to a circuit, inan embodiment.

FIG. 8 illustrates a method for communicating with, identifying,monitoring and controlling electronic devices connected to a circuit, inan embodiment.

FIG. 9 illustrates a system for communicating with, identifying,monitoring and controlling electronic devices connected to a circuit, inan embodiment.

FIG. 10 illustrates a system for communicating with, identifying,monitoring and controlling electronic devices connected to a circuit, inan embodiment.

FIG. 11 illustrates aspects of a clamp for connecting a multifunctioncommunication cube (MCC) to an electrical power circuit, in anembodiment.

FIG. 12 illustrates aspects of a clamp for connecting a multifunctioncommunication cube (MCC) to an electrical power circuit, in anembodiment.

FIG. 13 illustrates aspects of a clamp for connecting a multifunctioncommunication cube (MCC) to an electrical power circuit, in anembodiment.

While the invention is subject to various modifications and alternativeforms, specific embodiments thereof are shown by way of example in thedrawings and the accompanying detailed description. It should beunderstood, however, that the drawings and detailed description are notintended to limit the invention to the particular embodiments. Thisdisclosure is instead intended to cover all modifications, equivalents,and alternatives falling within the scope of the present invention asdefined by the appended claims.

DETAILED DESCRIPTION

One or more embodiments of the invention are described below. It shouldbe noted that these and any other embodiments are exemplary and areintended to be illustrative of the invention rather than limiting. Whilethe invention is widely applicable to different types of systems, it isimpossible to include all of the possible embodiments and contexts ofthe invention in this disclosure. Upon reading this disclosure, manyalternative embodiments of the present invention will be apparent topersons of ordinary skill in the art.

With the growth of the Internet of Things, existing devices are becomingnetworked in order to enable the monitoring, controlling, andcommunicating of the devices. Lighting and lighting systems are devicesthat are becoming networked in order to control power, color, andbrightness. Currently, the method for incorporating a control systeminto an existing lighting system may be carried out by running wire orcable from a control device/panel to the lighting system. The running ofthe wire or cable may cost $10,000 per floor and may require days toaccomplish. Additionally, the control device/panel may cost between$10,000 to $15,000. With such economics, the implementation of theInternet of Things to existing lighting systems has been slow in coming.

A method, apparatus, and system for monitoring, controlling, andcommunicating of devices may be described. The method, apparatus, andsystem may use a radio communication to power line communication bridgeand networking system for the monitoring, controlling, and communicatingof devices such as lighting systems. This method, apparatus, and systemmay not require the running of wire or cable and may be deployed inhours, not days, at a fraction of the cost of existing control systems.Since the apparatus may be used with any lighting fixture or lamp brand,the apparatus may be integrated into any existing lighting system.

FIG. 1 is a block diagram illustrating an apparatus for monitoring,controlling, and communicating in accordance with embodiments.

In embodiments, apparatus 100 may comprise at least one powernet controlunit and at least one communication cube. The powernet control unit(PCU) 105 may comprise a PCU housing 107, a system bus 109, at least oneprocessor 111, system memory 113, at least one non-transitory memoryunit 115, a power port 117, an internal battery 119, a communicationport 121, an inter-PCU/CC wireless module 123, and a GPS module 125, allof which may be directly or indirectly coupled to each other. Thecommunication cube (CC) 106 may comprise a CC housing 127, a system bus129, at least one processor 131, system memory 133, at least onenon-transitory memory unit 135, an internal battery 137, an inter-PCU/CCwireless module 139, at least one control port 141, at least one controlclamp 143, at least one monitor sensor 145, a RFID module 147, and aBluetooth module 149, all of which may be directly or indirectly coupledto each other. In the installation of the apparatus, the PCU 105 may bemounted on the back of a flat electrical strike plate and may be poweredby the internal battery 119 or by A/C power 151 through the power port117 in embodiments. In embodiments, the communication port 121 maycomprise at least one of a Wi-Fi radio, an Ethernet port, and a powerline communication (PLC) bridge and may allow for the communicationbetween powernet control units 105 and external control and monitoringdevices such as mobile device 153, local server 155, and/or remoteserver 157. For Wi-Fi, PLC, and Ethernet, communication may beestablished through a communication gateway 159 such as arouter/PLC/modem. Using a communication cube control web portal or acommunication cube control app (PCU/CC dashboard application), at leastone of the local servers 155 and the mobile device 153 may be used tocommunicate with the PCU 105 and the CC 106 through the communicationgateway 159. Additionally, the communication gateway 159 may beconnected to the Internet 161, thus making it possible for the remoteserver 157 and/or the mobile device 153, using a communication cubecontrol web portal or a communication cube control app, to communicatewith the PCU 105 and the CC 106. The PCU 105 may communicate with the CC106 through the inter-PCU/CC wireless module 123 of the PCU 105 with theinter-PCU/CC wireless module 139 of the CC 106. The inter-PCU/CCwireless modules 123, 139 may comprise at least one of a Bluetoothradio, 6LoWPan radio, and ZigBee radio. Bluetooth, 6LoWPan, and ZigBeemay encompass all past, current, and future versions of the wirelessprotocols. The powernet control units which are connected to the PLC maybe nodes which in turn may be in communication with the communicationcubes 106. Each PCU node may be capable of identifying the communicationcubes 106 which are connected to it. This network of communication cubes106 connected to PCU nodes which are connected via PLC may be referredto as a powernet.

In embodiments, the CC 106 may be mounted within a lighting fixture andmay be powered by the internal battery 137 or by one of the at least onecontrol clamp 143 spliced into the power line to the lighting fixture.The control clamp may be designed to splice the power line to a lightingfixture without having to shut down power to the lighting fixture ordevice. After splicing the power line, direct power to the lightingfixture may be removed and the CC 106 may now be capable of controllingthe lighting fixture or device, thus enabling control for dimming,color, and other primary and secondary functions such as, but notlimited to Li-Fi management and emergency controls. Since the controlclamp 143 is tapped into the power line, the control clamp 143 may alsobe able to provide power to the CC 106 through the control port 141. TheCC 106 may also comprise at least one monitor sensor 145 to monitor foroccupancy in the area of the lighting fixture as well as the lightingfixture location and status.

In embodiments, the RFID module 147 and Bluetooth module 149 of the CC106 may be used to establish a beacon. The RFID module 147 may be usedto monitor the space around the lighting fixture or device for any RFIDtransmitters. In a hospital setting, the RFID transmitters may bemounted onto tables, drug carts, wheel chairs, etc. The CC 106 may thenbe able to keep track of the RFID transmitters in the vicinity of thelighting fixture. The Bluetooth module 149 may be used to continuouslyping the area around the lighting fixture for any nearby Bluetoothenabled devices. The vast majority of phones and devices since 2006 mayrespond to this pinging, thus enabling the CC 106 to map and monitor thenumber of people that are carrying Bluetooth phones and devices that arein the vicinity of the lighting fixture. The processing of the RFID andBluetooth monitoring may be handled locally by the at least oneprocessor 131 of the CC 106. By having this map of people and things, ifa patient is looking for a particular facility within the hospital, thepath of least resistance (i.e. least congestion) for the patient to getto the particular facility may be determined from the data collectedfrom RFID monitoring and Bluetooth pinging. This path may be transmittedto the patient who is running the hospital's mobile application on aBluetooth enabled phone. In embodiments, the Bluetooth module 149 may beused to transmit offers, promotions, or other information to anindividual with a Bluetooth enabled phone running a particular store orpromotion mobile application. In such a scenario, if a customer isshopping at a grocery store and is running a store's mobile applicationon a Bluetooth enabled phone and the customer approaches the soft drinkaisle, the CC 106 may be able to determine that the customer is in thesoft drink aisle and may be able to present the customer offers andpromotions for products that are also in the soft drink aisle. The CC106 may present offers for products that are available since the CC 106may use its RFID module 147 to detect for products labeled with RFIDtags.

FIG. 2 is a block diagram illustrating an apparatus for monitoring,controlling, and communicating in accordance with embodiments.

In embodiments, apparatus 200 may comprise at least one powernet controlcommunication cube 205. The powernet control communication cube (PCCC)205 may comprise a housing 207, a system bus 209, at least one processor211, system memory 213, at least one non-transitory memory unit 215, apower port 217, an internal battery 219, a communication port 221, atleast one control port 223, at least one control clamp 225, at least onemonitor sensor 227, a GPS module 229, an RFID module 231, and aBluetooth module 233, all of which may be directly or indirectly coupledto each other.

In embodiments, the PCCC 205 may be mounted within a lighting fixture oron the back of a flat electrical strike plate and may be powered by theinternal battery 219 or by using one of the control clamps 225 coupledto the power port 217 to tap into a power line. Alternatively, the powerport 217 may draw its power internally from one of the control clamps225 connected to the control port 223. The communication port 221 maycomprise at least one of a Wi-Fi radio, a PLC bridge, an Ethernet port,ZigBee radio, 6LoWPan radio, and a Bluetooth radio and may allow for thecommunication between powernet control communication cubes 205 andexternal control and monitoring devices such as mobile device 235 andremote server 237. Bluetooth, 6LoWPan, and ZigBee may encompass allpast, current, and future versions of the wireless protocols. For Wi-Fi,PLC, and Ethernet, communication may be established through acommunication gateway 239 such as a router/PLC/modem. Using a PCCCcontrol web portal or a PCCC control app (PCCC dashboard application),the mobile device 235 may be used to communicate with the PCCC 205through the communication gateway 239. Additionally, the communicationgateway 239 may be connected to the Internet 241, thus making itpossible for at least one of the remote servers 237 and the mobiledevice 235, using a PCCC control web portal or a PCCC control app, tocommunicate with the PCCC 205. Using the Bluetooth radio of thecommunication port 221, the mobile device 235 may also be capable ofcommunicating with the PCCC 205 through the communication port 221. Thepowernet control communication cubes 205 may also communicate with eachother through the communication port 221 using the Bluetooth radio,6LoWPan radio, and/or ZigBee radio. The powernet control communicationcubes 205 which are connected to the PLC may be nodes which in turn maybe in communication with the powernet control communication cubes 205which may not be connected to the PLC. Each PCCC node may be capable ofidentifying the powernet control communication cubes 205 which may beconnected to it. This network of powernet control communication cubes205 connected to PCCC nodes which are connected via PLC may be referredto as a powernet. Lastly, the GPS module 229 may provide location datafor the PCCC 205 and may allow for the traceability of the PCCC 205 inevent of its theft.

In embodiments, the RFID module 231 and Bluetooth module 233 of the PCCC205 may be used to establish a beacon. The RFID module 231 may be usedto monitor the space around the lighting fixture or device for any RFIDtransmitters. In a hospital setting, the RFID transmitters may bemounted onto tables, drug carts, wheel chairs, etc. The PCCC 205 maythen be able to keep track of the RFID transmitters in the vicinity ofthe lighting fixture. The Bluetooth module 233 may be used tocontinuously ping the area around the lighting fixture for any nearbyBluetooth enabled devices. The vast majority of phones and devices since2006 will respond to this pinging, thus enabling the PCCC 205 to map andmonitor the number of people that are carrying Bluetooth phones anddevices that may be in the vicinity of the lighting fixture. Theprocessing of the RFID and Bluetooth monitoring may be handled locallyby the at least one processor 211 of the PCCC 205. By having this map ofpeople and things, if a patient is looking for a particular facilitywithin the hospital, the path of least resistance (i.e. leastcongestion) for the patient to get to the particular facility may bedetermined from the data collected from RFID monitoring and Bluetoothpinging. This path may be transmitted to the patient who is running thehospital's mobile application on a Bluetooth enabled phone. Inembodiments, the Bluetooth 233 may be used to transmit offers,promotions, or other information to an individual with a Bluetoothenabled phone running a particular store or promotion mobileapplication. In such a scenario, if a customer is shopping at a grocerystore and is running a store's mobile application on a Bluetooth enabledphone and the customer approaches the soft drink aisle, the PCCC 205 maybe able to determine that the customer is in the soft drink aisle andmay be able to present the customer offers and promotions for productsthat are also in the soft drink aisle. The PCCC 205 may present offersfor products that are available since the PCCC 205 uses its RFID module231 to detect for products labeled with RFID tags.

FIG. 3 is a block diagram illustrating an apparatus for monitoring,controlling, and communicating in accordance with embodiments.

In embodiments, apparatus 300 may comprise at least one powernet controlcommunication cube 305. The powernet control communication cube (PCCC)305 may comprise a housing 307, a system bus 309, at least one processor311, system memory 313, at least one non-transitory memory unit 315, apower port 317, an internal battery 319, a communication port 321, atleast one control port 323, and at least one control clamp 325, all ofwhich may be directly or indirectly coupled to each other.

In embodiments, the PCCC 305 may be mounted within a lighting fixture oron the back of a flat electrical strike plate and may be powered by theinternal battery 319 or by using one of the control clamps 325 coupledto the power port 317 to tap into a power line. Alternatively, the powerport 317 may draw its power internally from one of the control clamps325 connected to the control port 323. The communication port 321 maycomprise at least one of a Wi-Fi radio, a PLC bridge, an Ethernet port,ZigBee radio, 6LoWPan radio, and a Bluetooth radio and may allow for thecommunication between powernet control communication cubes 305 andexternal control and monitoring devices such as at least one of a mobiledevice 327 and a remote server 329. Bluetooth, 6LoWPan, and ZigBee mayencompass all past, current, and future versions of the wirelessprotocols. For Wi-Fi, PLC, and Ethernet, communication may beestablished through a communication gateway 331 such as arouter/PLC/modem. Using a PCCC control web portal or a PCCC control app(PCCC dashboard application), the mobile device 327 may be used tocommunicate with the PCCC 305 through the communication gateway 331.Additionally, the communication gateway 331 may be connected to theInternet 333, thus making it possible for at least one of the remoteservers 329 and the mobile device 327, using a PCCC control web portalor a PCCC control app, to communicate with the PCCC 305. Using theBluetooth radio of the communication port 321, the mobile device 327 mayalso be capable of communicating with the PCCC 305 through thecommunication port 321. The powernet control communication cubes 305 mayalso communicate with each other through the communication port 321using the Bluetooth radio, 6LoWPan radio, and/or ZigBee radio. Thepowernet control communication cubes 305 which may be connected to thePLC may be nodes which in turn may be in communication with the powernetcontrol communication cubes which are not connected to the PLC. EachPCCC node may be capable of identifying the powernet controlcommunication cubes 305 which may be connected to it. This network ofpowernet control communication cubes 305 connected to PCCC nodes whichare connected via PLC may be referred to as a powernet.

In embodiments, the PCCC 305 may be used to control a single lamp, asingle fixture, and/or a series of fixtures. For such an embodiment, thePCCC 305 may be mounted within the lighting fixture and may be poweredby the internal battery 319 or by one of the at least one control clamp325 spliced into the power line to the lighting fixture. The controlclamp 325 may be designed to splice the power line to a lighting fixturewithout having to shut down power to the lighting fixture or device.After splicing the power line, direct power to the lighting fixture maybe removed and the PCCC 305 may now be capable of controlling thelighting fixture, thus enabling control for dimming, color, and otherprimary and secondary functions such as, but not limited to Li-Fimanagement and emergency controls. Since the control clamp is tappedinto the power line, the control clamp may also be able to provide powerto the PCCC 305 through the power port 317. This embodiment wassimilarly disclosed in FIG. 2, except that in this embodiment, thecomponents not required for controlling a lighting system, (the at leastone monitor sensor, the GPS, the RFID, and Bluetooth) have beeneliminated.

In embodiments, the components for communication through thecommunication gateway may be separated from the components forcommunication between the powernet control communication cubes 305. Insuch an embodiment, the powernet control unit may comprise at least oneof the Wi-Fi radio, the Ethernet port, and the power line communication(PLC) bridge and the communication cube 305 may comprise at least one ofa Bluetooth radio, 6LoWPan radio, and ZigBee radio, as was similarlydisclosed in FIG. 1, except that in this embodiment, the components notrequired for controlling a lighting system (the at least one monitorsensor, the GPS, the RFID, and Bluetooth) have been eliminated.

FIG. 4 is a block diagram illustrating a method for monitoring,controlling, and communicating of devices in accordance withembodiments.

In embodiments, PCU code and CC code may be stored on the at least onePCU non-transitory memory unit and the at least one CC non-transitorymemory unit, respectively, and executed by the at least one PCUprocessor and by the at least one CC processor, respectively, to performa method 400 for monitoring, controlling, and communicating of devices.The method 400 illustrated in FIG. 4 may be performed by the apparatusillustrated in FIG. 1. Processing may begin in method 400 at block 405,wherein at least one control clamp may be spliced to the power lines ofat least one device.

At block 410, a PCU power line communication link may be established forcommunication between at least one powernet control unit in embodiments.

At block 415, a powernet control unit may be connected to acommunication gateway in order to enable communication with the powernetcontrol unit from a mobile device, local server, or remote server usinga PCU/CC dashboard application in embodiments.

At block 420, the PCU inter-PCU/CC wireless modules and the CCinter-PCU/CC wireless modules may be used to communicate between the atleast one powernet control unit and the at least one communication cubein embodiments.

At block 425, the CC inter-PCU/CC wireless modules may be used tocommunicate between the at least one communication cubes in embodiments.

At block 430, the PCU power line communication link may be used tocommunicate with the at least one powernet control unit in embodiments.

At block 435, the at least one communication cube with the spliced atleast one control clamp may be used to monitor and control the at leastone device in embodiments.

At block 440, the RFID modules and the Bluetooth modules of the at leastone communication cube may be used to create at least one RFID/Bluetoothbeacon in embodiments.

At block 445, the at least one monitor sensor of the at least onecommunication cube may be monitored in embodiments. The at least onemonitor sensor may be used to monitor for occupancy in the area of thedevice as well as the device location and status. Processing maysubsequently end after block 445 in embodiments.

FIG. 5 is a block diagram illustrating a method for monitoring,controlling, and communicating of devices in accordance withembodiments.

In embodiments, PCCC code may be stored on the at least onenon-transitory memory unit and may be executed by the at least oneprocessor to perform a method 500 for monitoring, controlling, andcommunication of devices. The method 500 illustrated in FIG. 5 may beperformed by the apparatuses illustrated in FIG. 2 and FIG. 3.Processing may begin in method 500 at block 505, wherein at least onecontrol clamp may be spliced to the power lines of at least one device.

At block 510, a power line communication link may be established forcommunication between at least one powernet control communication cubein embodiments.

At block 515, a PCCC may be connected to a communication gateway inorder to enable communication with the PCCC from a mobile device and/orremote server using a PCCC dashboard application in embodiments.

At block 520, the communication port may be used to communicate betweenthe at least one powernet control communication cube in embodiments.

At block 525, the power line communication link may be used tocommunicate between the at least one powernet control communication cubein embodiments.

At block 530, the at least one powernet control communication cube withthe spliced at least one control clamp may be used to monitor andcontrol the at least one device in embodiments.

At block 535, the RFID modules and the Bluetooth modules of the at leastone powernet control communication cube may be used to create at leastone RFID/Bluetooth beacon in embodiments.

At block 540, the at least one monitor sensor of the at least onepowernet control communication cube may be monitored. The at least onemonitor sensor may be used to monitor for occupancy in the area of thedevice as well as the device location and status. Processing maysubsequently end after block 540 in embodiments.

Embodiments described herein relate to a computer storage product withat least one non-transitory memory unit having instructions or computercode thereon for performing various computer-implemented operations. Theat least one memory unit are non-transitory in the sense that they donot include transitory propagating signals per se (e.g., a propagatingelectromagnetic wave carrying information on a transmission medium suchas space or a cable). The at least one memory unit and computer code(also can be referred to as code) may be those designed and constructedfor the specific purpose or purposes. Examples of at least one memoryunit include, but are not limited to: magnetic storage media such ashard disks, floppy disks, and magnetic tape; optical storage media suchas Compact Disc/Digital Video Discs (CD/DVDs), Compact Disc-Read OnlyMemories (CD-ROMs), and holographic devices; magneto-optical storagemedia such as optical disks; carrier wave signal processing modules; andhardware devices that are specially configured to store and executeprogram code, such as Application-Specific Integrated Circuits (ASICs),Programmable Logic Devices (PLDs), Read-Only Memory (ROM), andRandom-Access Memory (RAM) devices.

Examples of computer code include, but are not limited to, micro-code ormicro-instructions, machine instructions, such as produced by acompiler, code used to produce a web service, and files containinghigher-level instructions that are executed by a computer using aninterpreter. For example, embodiments may be implemented using Java,C++, Python, C, or other programming languages (e.g., object-orientedprogramming languages) and development tools. Additional examples ofcomputer code include, but are not limited to, control signals,encrypted code, database code, and compressed code.

As discussed, a single multifunction communications cube (MCC) may havemultiple means or subsystems for receiving and transmitting digitalinformation. It will be understood that a multifunction communicationcube (MCC) may include all, or a subset, of the same or similarcomponents, features, and functionality of apparatus 100, apparatus 200,and apparatus 300 described in detail elsewhere in this application. TheMCC may use its communications subsystems or inputs (Wi-Fi, ZigBee,Bluetooth, PCL, Ethernet, etc.) to generate a “digital impression” or“digital profile” including digital impression information of thedevices in its environment. The digital impression may containessentially all, or a subset of, signal information across all of theCC's detection means for each and every device that the MCC can detect.The digital impression information collected about different devices inthe environment of the MCC may differ in relation to signal informationavailable and collected by the CC. The MCC may monitor all of the inputssimultaneously, or in any suitable order to generate such a digitalimpression. Monitoring of inputs by the MCC may include monitoring allor a subset of communications subsystems of the CC. This digitalimpression may be limited only by the inherent limitations of thedifferent input methodologies or input subsystems of the CC. In anembodiment, for example, the CC's ability to monitor devices via its PLCinputs may be limited to devices connected to an electrical circuitaccessible to the CC, while the devices observable via the CC'sBluetooth and Wi-Fi inputs may be limited to the communication receptionranges determined by each device's Bluetooth antenna range and Wi-Fiantenna range. The signal information from all inputs available to theMCC may be aggregated to generate the digital impression. Multiple CCswith overlapping sensor ranges may have separate digital impressionsthat contain devices that overlap, or alternatively, may be aggregatedtogether to create a single, more thorough or complete digitalimpression of the devices around the plurality of networked CCs. In anembodiment, for example, a first MCC and second MCC in communication,directly or indirectly via other intermediate CC's relayingcommunications information between the first MCC and second CC, may havecombined, coordinated, or cooperative capability to identify, monitor,and interact with devices via PLC inputs connected to any electricalcircuit accessible or connected to either the first MCC and the secondCC, and further may have combined, coordinated or cooperative capabilityto identify, monitor and interact with the same or other devices viaBluetooth and Wi-Fi inputs within wireless communication range of boththe first MCC and second CC. In such an embodiment, for example, digitalimpressions of each of a plurality of devices may include digitalimpression information obtained via PLC inputs, Bluetooth inputs, andWi-Fi inputs, of each and every device observable, directly orindirectly, by the first MCC and second CC.

In an exemplary scenario, if a MCC is installed into a powerline circuitin a room with a Wi-Fi enabled smart TV that is connected to the samepowerline circuit as the CC, a Bluetooth and Wi-Fi enabled cell phonesitting by itself on a desk in the next room over, and a ZigBee enabledsmoke detector connected to a separate powerline circuit in the hallbetween the two rooms, the MCC may receive both a PLC signal and a Wi-Fisignal from the TV, both Wi-Fi and Bluetooth signals from the cellphone, and a ZigBee signal from the smoke detector. The digitalimpression generated by the MCC would comprise all of these signalstogether.

The CC's onboard processor may aggregate this sensor data in order togenerate the digital impression of the CC's environment. The MCC maythen use its processor and information contained on its onboard memoryto identify digital signatures of the different devices constituting thedigital impression. If the digital impression cannot be disambiguated todetermine the unique signatures identifying the constituent devices, theMCC may use one or more of its communications pathways to transmit thedigital impression to a remote server, which may have access to moredata and processing capabilities than the CC's onboard hardware in orderto disambiguate the digital impression and determine what devices arebeing sensed by the CC. Once the digital impression has beendisambiguated and the unique devices sensed by the MCC are identifiedthat information along with control information for those devices may becommunicated from the remote server back to the MCC through a suitablecommunication network. The unique device information may compriseinformation such as the make and model of the device, and may furthercomprise control information including, but not limited to controlsignals compatible with the identified device through one or morecommunications means, and a hierarchy of what communications means arepreferred for controlling said device. Whether or not the MCC candetermine the devices constituting the digital impression throughonboard processing versus offboard processing at a remote server may bea question of the CC's form factor and current hardware limitations.

Once the MCC has either determined the identity of the devices that itsensed in its digital impression, or has received such information fromthe remote server, the MCC may then use any of the output methodsavailable to it to communicate with and control the unique devices whosesignals were include in the CC's digital impression. The determinationof what communication means should be used to control which uniquedevice may be associated with the information used to identify of theunique devices, and may be determined when the unique devices areidentified. This control and control preference information may bestored either on the CC's or on the remote server's memory. Thisselection of the means by which to control the devices may be limited tothe manner in which the MCC can communicate with that particular device(it would not be helpful for the MCC to try to control a Wi-Fi enabledTV via Wi-Fi if either the MCC does not possess Wi-Fi functionality, orif the MCC is in only powerline communication with the TV).

Continuing with the example provided above, once the MCC has formed adigital impression of its environment, including the PLC signature ofthe TV, the Wi-Fi signatures of the TV and the smartphone, the Bluetoothsignature of the smartphone, and the ZigBee signature of the smokedetector, it may transmit this impression to a remote server, andreceive back from the server information indicating the three devicesand their control preferences. The stored device information indicatesthat the TV may be controlled via PLC, infra-red (IR), and Wi-Fi, butprefers to be controlled via IR or Wi-Fi; the smartphone prefers to becontrolled by Bluetooth rather than Wi-Fi; and the smoke detector can becontrolled by PLC or ZigBee and has no preference on which is better. Insuch a case, the MCC would control the TV via Wi-Fi as it is preferredover PLC and the MCC does not possess IR; the smartphone via Bluetoothas it is preferred over PLC; and the smoke detector via ZigBee as it isthe only connection that the MCC has to that device.

In embodiments, the MCC may be limited to having fewer than all of thepossible input and communications means. For example, one MCC may beconfigured for Ethernet and PLC communication only, while another MCCmay be configured for Ethernet and Bluetooth communication only, whileyet another MCC may be configured for wireless, Bluetooth, and PLCcommunication. Any permutation or combination of communication means maybe provided for on any specific MCC without departing from the scope ofthis disclosure. Embodiments without the capability of at least onecommunications means may be termed a “limited CC”. Multiple differentlylimited CCs, for example one that is limited to Bluetooth and PLC, andone limited to Bluetooth and Wi-Fi, may communicate together via theirshared communication protocol. In such an example the Bluetooth and PLClimited MCC may relay its digital impression to a remote server by usingits shared communication protocol (in this case Bluetooth) to relayinformation to the other CC, which may then transmit both its digitalimpression and the digital impression received from the other limitedMCC to the remote server via Wi-Fi.

In embodiments, a single MCC may be configured to use any and allsuitable communications means.

Multiple CCs may be networked together via suitable communicationsnetworks. Multiple CCs in a particular physical location may beconsidered a “node”. Multiple nodes may be connected together to form anetwork or MCC network. In embodiments, a single node may constitute anetwork or MCC network.

The CCs in a node may transmit and receive communications with oneanother in order to determine which of the CCs has the strongestconnection to a communication network capable of transmittinginformation to a target device external to the node. The other CCs ofthe node may then relay information to the target device through the MCCwith said strongest connection. The MCC through which the node'sinformation is relayed may update in the event that the connectionstrength changes. This may allow all of the CCs in the node to be ableto communication with the remoted device even if any particular MCCcannot directly communicate with said remote device. Furthermore, thisrelaying of information between networked CCs does not have to bedirect, and may be indirect. For example, a first MCC may transmitinformation to a second CC, which may in turn transmit the informationfrom the first MCC to a third CC, that may then transmit the informationfrom the first MCC to a remote device. This ability to relay informationthrough a series of networked CCs may also provide for a “gap jumping”ability, where an MCC that is not capable of transmitting directly to aremote device may relay information through one or a series of connectedCCs until one of them is able to establish a connection to the remotedevice.

This relaying of information between networked CCs does not have to bedirect, and may be indirect. In embodiments, a plurality of CCsconstituting a node may be connected together in a mesh networkconfiguration. Such a mesh network of CCs, for example, may relayinformation using either a flooding technique or a routing technique. Toensure all its paths' availability, the network may allow for continuousconnections and should be able to reconfigure itself around brokenpaths, using self-healing algorithms. Self-healing allows arouting-based network to operate when a node breaks down or when aconnection becomes unreliable. Utilizing such a mesh networkconfiguration, a first MCC may transmit information to a second CC,which may in turn transmit the information from the first MCC to a thirdCC, that may then transmit the information from the first MCC to aremote device. This ability to relay information through a series ofnetworked CCs may also provide for a “gap jumping” ability, where an MCCthat is not capable of transmitting directly to a remote device mayrelay information through one or a series of connected CCs until one ofthem is able to establish a connection to the remote device.

In an embodiment, a plurality of CCs may cooperate to identify and sharedigital impression information regarding network routers and networksecurity devices, such as network security packet sniffers, of a securednetwork for evading detection by the secured network routers and networksecurity devices while identifying, monitoring, interacting with, andcontrolling devices on the secured network. The plurality of CCs mayestablish and communicate over a separate mesh communications network,or over any other network accessible to the plurality of CCs. Inembodiments, where the plurality of CCs may have developed and shared,or may have received from a remote server, digital impressioninformation regarding network routers and network security devices at anestablished or acceptable confidence level, one or more of the pluralityof CCs may communicate over a separate mesh network established betweenthe plurality of CCs, and/or may communicate over the secured networkaccording to protocols that are unidentifiable or undetectable by thesecured network routers and network security devices so as to remain“dark” and undetected. In embodiments, one or more of the plurality ofCCs may also communicate over the secured network according to protocolsthat are compatible, identifiable, or detectable by the secured networkrouters and network security devices so as to spoof or simulate otherdevices known to be on the network, or that might belong on the network,to misinform the secured network routers and network security devicesregarding the security or unsecured status of the secured network,and/or also to misinform network security devices regarding operationsand operating status of devices identifiable, or known, by the CCs. Itwill be understood that the term “devices” may include firmware andsoftware associated with hardware devices or nodes.

In embodiments, CCs may automatically assign themselves identifiers.Automatic identification of the CCs may be performed, for example, inaccordance with a 6LoPan protocol. A plurality of networked CCs mayautomatically share digital impression information for devicesdetectable by, or known to, any of the plurality of CCs, andautomatically share instructions for monitoring, interacting with, andcontrolling such devices.

In an embodiment utilizing PLC monitoring and control of a device, theMCC may monitor the power line signals going through the circuit intowhich it is spliced. The MCC may also monitor wireless signals through asignal array including but not limited to WIFI, Bluetooth, RFID, ZigBee,and Specific Application Frequencies. The monitoring may be performed bythe processor portion of the CC. The power line signals comprisewaveforms that correspond to each of the electric devices on thecircuit. Similarly, wireless devices can be identified by theirrespective MAC and IP address. A problem is presented that, becausethese signals are all running through the same power line, or throughthe same space in the instance of wireless signals, and into the sameMCC device, the signals may become jumbled together or conflated,creating “signal noise”. This signal noise on the PLC input to the MCCis a constituent part of the inputs that the MCC aggregates together togenerate the digital impression. These individual signals within thedigital impression and the signal noise must be disambiguated in orderto identify the unique signals that are indicative of each unique deviceon the circuit. Signal strength and range are determined by a number offactors including but not limited to: whether there are physicalbarriers in between the transmitting and receiving devices, whetherthere is competing signal traffic, the relative strength of the signalbeing transmitted, the type of signal being transmitted, and thefrequency the signal is being transmitted on.

In some embodiments, to disambiguate the unique device waveforms fromsignal noise of the PLC circuit, as well as the other signals picked upby the other input means or subsystems possessed by the MCC whichconstitute the digital impression, it is necessary to possess or accessa database of signal waveforms and other unique device signatures andtheir associated devices. Such a database may comprise millions ofunique signals each identifying a unique electrical device. For thisreason, it may be impractical to maintain this database on the memory ofan MCC itself. Instead a remote device, such as a remote server, may beused to store the unique signal information and to do or perform theprocessing of the data needed to identify and disambiguate theconstituent unique signals that comprise the signal noise or conflatedsignals. To provide the signal noise information from the MCC to theremote server, the MCC may record a portion of the single noise andtransmit it, via suitable network connection, to the server. The servermay run an algorithm to analyze the segment of signal noise receivedfrom the MCC to differentiate the individual signals from the signalnoise. Once the individual signals have been identified, the server canmatch them to signals from the database of unique signals and identifytheir respective electrical devices. In an embodiment, an MCC or remoteserver may process signal noise or conflated signals to eliminate,adjust or compensate for signals of identified devices in the jumbledsignal noise or conflated signals, and thus simplify or reduceprocessing steps and time required to identify remaining devices fromtheir characteristic signals remaining in the adjusted or compensatedsignal noise or conflated signals.

Once the devices associated with the disambiguated signals have beenidentified by the server, the server can then transmit the identity ofthe electrical devices associated with the portion of signal noisetransmitted to it back to the CC. Once the MCC has received the identityof the devices on its circuit from the server, it may then use signalcommands for the associated devices to control the devices on itscircuit. Unlike the unique signal identification information stored onthe server, which can comprise massive amounts of information, signalcommands may be compatible between related types of electronic devicesand therefore require significantly smaller amounts of memory to store.Therefore, in some embodiments, the database of signal commands may bestored locally in the MCC in a local memory. Once the MCC has determinedor received signal commands associated with the electric devices on its'circuit, the MCC can then use its processor to transmit waveformscorresponding to the signal commands associated with a particular deviceto control certain known characteristics of the particular device'soperation.

In embodiments, the manner in which the MCC may be able to control thedevices on its circuit vary depending on the device. For powermodulation where there may no digital management capability. Forexample, for incandescent light bulb or older TVs, the only options willbe off/on dim up/dim down. Those “commands” are managed throughincreasing or decreasing the voltage and/or current being transmitted tothe device being controlled through the powerline. The MCC mayeffectuate such a modulation of voltage and/or current through the useof a series of circuits, or through a series of resistors/transistors ifanalog. For other devices, which may be controlled wirelessly, the MCCmay provide control signals to the device through a suitable wirelesscommunication means (e.g. Wi-Fi, Bluetooth, IR, etc.) rather thanthrough modulation of the waveform of the power line into which thedevice is connected. For example, The MCC may identify a smart TVthrough the power line and identify it as a TV, and may then implement acontrol profile identified as usable via Wi-Fi or IR. The preference ofcontrol methodology for the specific device may associated with theunique device once it is identified. The preferred control means may belimited by the communications capabilities of the MCC that is trying tocontrol the device.

Generally, not all electrical circuits in a building are connected. Evencircuits within the same breaker panel are often not directly connected.Whether it is for meeting code requirements, load limit restrictions,security, redundancy, reduction of single point failure, or convenience,multiple distinct electrical circuits are used. Addressing these hurdleswhen implementing a network is an additional advantage of the MCC overcurrent technologies. Multiple CC's can be networked together to createa mesh network spanning large open areas. Multiple CC's can also beconnected to communicate along that circuit over great distances andthrough physical barriers like floors, walls, and ceilings. These CCsmay be able to communicate with one another through alternate compatiblecommunications means or subsystems if one such means of communication isnot available. For example, if two CCs both have Wi-Fi functionality andare within Wi-Fi range of one another, but are not connected to the samepowerline circuit, the two CC's may communicate through the Wi-Finetwork (or indirectly through the MCC mesh network) rather thancommunicating via PLC. Since all CC's in proximity are able tocommunicate as programmed (meeting designated network securityrequirements), either wirelessly, wired, or both, a network of CC's can“jump” significant distances between electrical circuits, throughphysical barriers like floors and walls where wireless signals would nototherwise penetrate via powerline, or through electromagnetic barriers,via a wireless and/or wired mesh network. It will be understood thatelectromagnetic barriers may include, for example, a Faraday cageelectromagnetic barrier.

As shown in FIGS. 11-13, a multifunction communication cube (MCC) may beconnected or spliced into an electrical circuit without interrupting thedownstream power flow of the circuit through use of a specially designedclamp. Referring to FIG. 11, clamp 1100 may be an insulated tube 1105that has a single, non-conductive (glass, ceramic, etc.) blade 1110. Insome embodiments, clamp 1100 may include a conductive blade 1115 thatmay be narrower at the top than at the bottom, and made of a conductivematerial (copper at minimum) and a contact pad 1130 connected to the topof the conductive blade via solder, wire etc. The contact pad 1130allows for current to flow from the inside of the insulated tube 1105 tothe outside of the insulated tube 1105. The contact pads 1130 have awire connector 1125 that may transfer power from the insulated tube 1105to an external device (not shown). It will be understood that thisdesign accommodates a single wire 1120 conductor. FIG. 12 illustratesclamp 1200 in an alternative embodiment for tapping a single wire 1120conductor. Clamp 1200 may accommodate one wire and may include twoconductive blades 1115, positioned on opposite sides of thenon-conductive blade 1110. Each of the two conductive blades 1115 may beattached to exiting wires 1125, and 1210, which may carry signals fromeach end of the severed wire 1120. In embodiments, such a clamp maysplice the MCC into a conductor of a circuit while simultaneouslytransmitting current to devices on the circuit downstream of the CC.

To facilitate this non-interrupting splicing the power line wire may belaid inside of the insulated tube 1105. Once the wire 1120 is inside ofthe insulated tube 1105, the insulated tube 1105 is closed driving thenon-conductive blade 1110 through the wire 1120 severing the connectionbetween the upstream power source (upstream) and downstream powereddevice (downstream), and driving the conductive blades 1115 on eitherside of the non-conductive blade 1110 through the wire's insulation,causing the conductive blades 1115 to make electrical contact with thewire 1120 simultaneously. Contact being made with the wire 1120 andsevering said wire 1120 will cause power to redirect through theconductive blades 1115. Power re-directed to the pads may be transferredfrom the pads on the outside of the tube to a wiring harness. Thisallows power to be diverted through the wire harness from the upstreamside of the conductive blades to an external device (in this instance toCC). Once the MCC and clamp are connected to the power line, the powersignal is processed, analyzed, manipulated etc. in the CC. Power maythen be transmitted from the MCC through the clamp, through the wireharness connected to the downstream side and through the contact pad.Additionally, the MCC may provide signals via the power line by passingpower signals and/or additional signals from the MCC through the contactpads to the conductive blades. The signals are then passed from theconductive blade to the downstream section of the wire in contacttherewith. The power signals then pass along the wire to the devicebeing powered, thus completing a single leg of the circuit. In theinstance of a single wire clamp the process needs to be repeated forother the leg of the circuit.

Referring to FIG. 13, for a double-wire embodiment, in which the clamp1300 allows for splicing into a circuit having a positive and a negativewire, the tube 1105 is designed to have two channels 1315, 1320. Each ofthe two wires 1325, 1120 are laid inside of the tube 1105, one wire ineach channel. The tube 1105 is closed driving the nonconductive blade1110 through each of the wires 1120, 1325 severing their connectionbetween the upstream power source (upstream) and downstream powereddevice (downstream), and driving the conductive blades 1115 on eitherside of the non-conductive blade 1110 through the wire's insulationcausing the conductive blades 1115 to make electrical contact with theconductor of each wire 1120, 1325 simultaneously. The tube 1105 closingwill drive the conductive blades 1115 through the insulation around therespective wires 1120, 1325 in each channel 1315, 1320 until theconductive blades 1115 make contact with the conductive portions of thewires 1120, 1325. Contact being made with the wire 1120, 1325 andsevering the wire 1325, 1120 will cause power to redirect through theconductive blades 1115. It is important to note that there should be aseparate set of conductive blades for each wire into which the clamp isbeing used to splice. The separate sets of conductive blades allow forre-direction of the signals from each wire through the associated set ofconductive blades without shorting out any connection. Power re-directedto the pads may be transferred from the pads on the outside of the tubeto output wires 1125, 1210, 1330, 1335. This allows power to be divertedthrough the wire harness from the upstream side of the conductive bladesto an external device (in this instance to CC). Once the MCC and clampis connected to the power line power is processed, analyzed, manipulatedetc. in the CC. Power may then be transmitted from the MCC through theclamp, through the wire harness connected to the downstream side andthrough the contact pad. Additionally, the MCC may provide signals viathe power line by passing power/signals from the MCC through the contactpads to the conductive blades. The signals are then passed from theconductive blade to the downstream section of the wire they are makingcontact with. The power then passes along the wire to the device beingpowered, thus completing a single leg of the circuit. In the instance ofa single wire clamp the process needs to be repeated for other the legof the circuit. In the instance of a double wire clamp the process isclosed due to both positive and negative wire running through the sameclamp.

In embodiments, the clamp may be configured for any number of wires. Forsuch embodiments, the clamp may comprise a number of wire channels equalto the number of wire into which the clamp is to splice. The clampshould additionally comprise a separate set of conductive blades forsevering and re-directing the signal from each wire. The conductiveblades should be separated such that no short circuiting of any of thewires occurs due to electrical contact between one conductive blade andmultiple wires. A single non-conductive blade may be used to sever anynumber of wires as it is non-conductive and thus will not cause anyshort circuiting.

In embodiments, the conductive blades may comprise a V-shape.

Referring to FIG. 6, in an embodiment disclosed subject matter includesmethod 600 for identification, communication, monitoring, and control ofelectronic devices connected to a circuit. Method 600 may includeconnecting 605 a multifunction communication cube (CC) to the circuit.It will be understood that the multifunction communication cube (CC) mayhave a construction, features and functionality as described elsewherein this application. A subject circuit may be, for example, anelectrical circuit of a building to provide power to electronic devices,or any other suitable circuit. The MCC may be connected to at least oneconductor of the subject circuit via a clamp as described hereinabove,or may be otherwise connected or installed in conductive relationshipwith at least one conductor or wire of the subject circuit. Method 600may include recording 610 signal noise from the circuit by themultifunction communication cube (CC) to provide recorded signal noise.Method 600 may include transmitting 615 the recorded signal noise to aremote device, such as a remote server, via a connection to an externalcommunications network. It will be understood that, for example, theremote server may be accessed over the Internet. Method 600 may includedetermining 620 constituent unique device waveforms in the recordedsignal noise, by the remote device or server, such as by a processor ofthe remote server comparing the recorded signal noise with samples ofknown unique device waveforms of known devices from a database. It willbe understood that one suitable database of known devices and devicewaveforms may be, for example, the MIT Project Dilon signal fingerprintdatabase. Method 600 may include identifying 625 devices connected tothe subject circuit by identifying unique device waveforms of knowndevices that produce same from the database, by the remote server.Method 600 may include transmitting 630 identifications of devices tothe communications cube (CC) from the remote server over a suitablecommunications network. Method 600 may include associating 635 commandsignals with each identified device connected to the subject circuit bya processor of the communications cube (CC). It will be understood thatcommand signals of devices may be obtained from local memory of thecommunications cube (CC). Method 600 may include generating 640 commandsignals associated with identified devices by the processor of thecommunications cube (CC) on the subject circuit, to interact with andcontrol aspects of such identified devices. It will be understood that,in an embodiment, command signals may also be communicated to identifieddevices over an output other than the subject circuit, such as over awireless connection to an identified device, via a suitable wirelesssubsystem of the communications cube (CC). It will be understood thatmethod 600 may be performed by any suitable system such as, for example,system 900 shown in FIG. 9.

Referring to FIG. 7, in an embodiment disclosed subject matter includesmethod 700 for identification, communication, monitoring, and control ofelectronic devices at a site. Method 700 may include installing 705 amultifunction communication cube (CC) at the site. It will be understoodthat each multifunction communication cube (CC) may have a construction,features and functionality as described elsewhere in this application. Asite may include, for example, at least one subject wired circuit, atleast one subject wireless communication channel, or both, connected toat least one subject electronic device. A subject circuit may be, forexample, an electrical circuit of a building to provide power toelectronic devices, or any other suitable circuit such as a wiredEthernet connection of such a building. The MCC may be connected to atleast one conductor of the subject circuit via a clamp as describedhereinabove, or may be otherwise connected or installed in conductiverelationship with at least one conductor or wire of the subject circuit.A subject wireless communication channel may be, for example, a ZigBee,Wi-Fi or Bluetooth wireless communication channel or infrastructureassociated with the building or structure at the site, associated with anetwork at the site, or associated with subject wireless electronicdevices present at the site. Method 700 may include pinging 710 over allavailable inputs of the MCC to respective subject circuits and subjectwireless communications channels. Method 700 may include receiving 715device signal information, signal noise, and/or conflated device signalsvia available inputs of the MCC from the respective subject circuits andsubject wireless communications channels. Method 700 may includeaggregating 720 by the MCC device signal information, signal noiseand/or conflated device signals recorded from each of the inputs of theCC, to generate an aggregated digital impression or multidimensionaldigital impression information including recorded signal noise andrecorded wireless communications information. Method 700 may include MCCdisambiguation determining or analyzing 725 constituent unique devicewaveforms in recorded device signal information, signal noise and/orconflated device signals, by a local processor of the MCC comparing therecorded device signal information, signal noise and/or conflated devicesignals with samples of known unique device waveforms of known devicesand/or devices previously or contemporaneously identified at the site,which are stored in MCC memory and/or stored in a local database of theMCC or any MCC in communication with the subject MCC at the site. Method700 may include local identifying 735 of devices from the aggregateddigital impression information by the CC. Method 700 may includetransmitting 740 aggregated digital impression information from the MCCto a remote device, such as a remote server, via a connection to anexternal communications network. It will be understood that, forexample, the remote server may be accessed over the Internet. Method 700may include remote disambiguation determining or analyzing 745aggregated digital impression or multidimensional digital impressioninformation including recorded signal noise and recorded wirelesscommunications information to identify constituent unique devicewaveforms in recorded device signal information, signal noise and/orconflated device signals, and to identify constituent device wirelesscommunications properties or wireless constituent device identificationinformation, by a remote processor of the remote server comparing therecorded device signal information, signal noise and/or conflated devicesignals with samples of known unique device waveforms of known devicesand/or devices previously or contemporaneously identified at the site,and comparing recorded wireless communications information with knownwireless communications information or properties of known devices ordevice types to identify constituent device wireless communicationsproperties or wireless constituent device unique identificationinformation, which are stored in memory associated with the remoteserver and/or stored in a remote database. It will be understood thatone suitable database of known devices and device waveforms andidentification information may be, for example, the MIT Project Dilonsignal fingerprint database. Analyzing 745 may include identifyingdevices connected to a subject circuit or capable of communicating overa subject wireless communication channel or wireless infrastructure atthe site, by identifying unique device waveforms of known devices thatproduce same, or identifying device wireless communications informationor properties of known device, from the database, by the remote server.Method 700 may include transmitting 750 identifications of devices tothe communications cube (CC) from the remote server over a suitablecommunications network. Method 700 may include associating 755 devicecontrol pathways, such as command signals, with each identified deviceconnected to a subject circuit connected to the MCC or visible over awireless communications connection or channel to the CC, by a processorof the communications cube (CC). It will be understood that commandsignals of devices may be obtained from local memory of thecommunications cube (CC). Method 700 may include generating ortransmitting 760 command signals or control associated with identifieddevices by the processor of the communications cube (CC) on the subjectcircuit, and/or over a wireless communications connection or channel, tointeract with and control aspects of such identified devices. It will beunderstood that, in some embodiments, command signals or control signalsmay be communicated to such identified devices over a wirelessconnection to an identified device, via a suitable wireless subsystem ofthe communications cube (CC). It will be understood that method 700 maybe performed by any suitable system such as, for example, system 900shown in FIG. 9.

Referring to FIG. 8, in an embodiment disclosed subject matter includesmethod 800 for identification, communication, monitoring, and control ofelectronic devices at a site or node. Method 800 may include installing805 a plurality of multifunction communication cubes (CC's) at the siteor node. It will be understood that each multifunction communicationcube (CC) may have a construction, features and functionality asdescribed elsewhere in this application. A site may include, forexample, at least one subject wired circuit, at least one subjectwireless communication channel, or both, connected to at least onesubject electronic device. Method 800 may include self-identifying 810by each MCC via a self-identification protocol. A suitableself-identification protocol may be embodied in processor accessiblecode, such as software code. In an embodiment, a suitableself-identification protocol is 6LowPan. Method 800 may include pinging815 by each MCC all sensory inputs, including available communicationsinputs, to identify all other CC's in the node. Method 800 may includeidentifying 820 by each MCC signal strength to an external target devicesuch as, for example, a wireless network access point or wirelesscommunications transceiver, for communication to a remote server over anexternal communications network such as, for example, the Internet. Itwill be understood that a suitable wireless communications transceivermay include a transceiver of a wireless mobile data network or cellularcommunications network. Method 800 may include identifying 820 signalstrengths from each MCC to an external target device. Method 800 mayinclude determining 825 whether each MCC having a relatively weakersignal strength to an external target device can see and enter intocommunications with another MCC having relatively strongest signalstrength to an external target device. Method 800 may include directrouting 830 of information by all CC's in the node through an MCCidentified as having the relatively strongest signal strength to anexternal target device. Method 800 may include indirect routing 835 ofinformation by any CC's in the node to an intermediary MCC and from theintermediary MCC through an MCC identified as having the relativelystrongest signal strength to an external target device. Method 800 mayinclude receiving 840 information by an MCC identified as having therelatively strongest signal strength to an external target device, fromother CC's in the node. Method 800 may include transmitting 845information by the MCC identified as having the relatively strongestsignal strength to an external target device, to said external targetdevice. It will be understood that the particular MCC identified ashaving relatively strongest signal strength to an external target devicemay change from time to time as conditions at the site change, or asexternal target devices such as external wireless infrastructurechanges. It will be understood that method 800 may be performed by anysuitable system such as, for example, system 900 shown in FIG. 9.

Referring to FIG. 9, in an embodiment disclosed subject matter includessystem 900 for identification, communication, monitoring, and control ofelectronic devices at a site. System 900 may include a first node 906and second node 908 at the site. The first node 906 and second node 908may be identical, except that each node may be connected to differentinfrastructure at the site and/or each node may include different setsor groups of multifunction communication cubes (MCC's). The first node906 is exemplary and will be described in further detail. First node 906may include a plurality of multifunction communication cubes (MCC's)(914, 916, 918, 920) at the site. It will be understood that eachmultifunction communication cube (914, 916, 918, 920) may include all,or a subset, of the same or similar components, features, andfunctionality of apparatus 100, apparatus 200, and apparatus 300described in detail elsewhere in this application. In the particularembodiment shown in FIG. 9, the multifunction communication cubes(MCC's) are more specifically characterized by reference to such devicesincluding wireless communications subsystems (MCCW1, MCCW2), and othersuch devices including both wireless communications subsystems and wiredor powerline connections (designated MCCW+P1, MCCW+P2). First node 906may include, for example, multifunction communication cubes (MCC'sdesignated MCCW+P1, MCCW+P2) connected to a subject wired circuit havingat least one subject wired device (PDI, PD2) connected thereto. Asubject circuit may be, for example, an electrical circuit of a buildingto provide power to electronic devices, or any other suitable circuitsuch as a wired Ethernet connection of such a building. As shown in FIG.9, each MCC may be connected to at least one conductor of the subjectcircuit via a clamp as described elsewhere and shown in FIGS. 11-13, ormay be otherwise connected or installed in conductive relationship withat least one conductor or wire of the subject circuit. First node 906may include, for example, multifunction communication cubes (MCC'sdesignated MCCW1, MCCW2, MCCW+P1, MCCW+P2) each connected to subjectwireless communication channels and providing wireless connections toeach subject wireless electronic device (WDI, WD2) within wirelessreception and transmission range of such multifunction communicationcubes (MCC's designated MCCW1, MCCW2, MCCW+P1, MCCW+P2). A subjectwireless communication channel may be, for example, a ZigBee, Wi-Fi orBluetooth wireless communication channel or infrastructure associatedwith the building or structure at the site, associated with a network atthe site, or associated with subject wireless electronic devices presentat the site. Each MCC may ping over all available inputs (P1, P2) of theMCC to a subject wired circuit to subject wired devices (PDI, PD2) andto subject wireless communications channels to subject wireless devices(WDI, WD2). The plurality of multifunction communication cubes (MCC'sdesignated MCCW1, MCCW2, MCCW+P1, MCCW+P2) each may also includesuitable wireless communication subsystems, such as 6LoWPAN subsystems,providing wireless communication channels and enabling wirelessconnections with each other multifunction communication cube (MCC'sdesignated MCCW1, MCCW2, MCCW+P1, MCCW+P2) within wireless reception andtransmission range of such multifunction communication cubes (MCC'sdesignated MCCW1, MCCW2, MCCW+P1, MCCW+P2). Each of the multifunctioncommunication cubes (MCC's designated MCCW1, MCCW2, MCCW+P1, MCCW+P2)may receive device signal information, signal noise, and/or conflateddevice signals via available inputs of the MCC from the respectivesubject circuits and subject wireless communications channels. Each ofthe multifunction communication cubes (MCC's designated MCCW1, MCCW2,MCCW+P1, MCCW+P2) may aggregate by an MCC local processor device signalinformation, signal noise and/or conflated device signals recorded fromeach of the inputs of the CC, to generate an aggregated digitalimpression or multidimensional digital impression information includingrecorded signal noise and recorded wireless communications information.Each of the multifunction communication cubes (MCC's designated MCCW1,MCCW2, MCCW+P1, MCCW+P2) may perform disambiguation determining oranalyzing of constituent unique device waveforms in recorded devicesignal information, signal noise and/or conflated device signals, by thelocal processor of the MCC comparing the recorded device signalinformation, signal noise and/or conflated device signals with samplesof known unique device waveforms of known devices and/or devicespreviously or contemporaneously identified at the site, which are storedin MCC memory and/or stored in a local database of the MCC or any MCC incommunication with the subject MCC at the site. Each of themultifunction communication cubes (MCC's designated MCCW1, MCCW2,MCCW+P1, MCCW+P2) may perform local identifying of devices from theaggregated digital impression information by the MCC. Each of themultifunction communication cubes (MCC's designated MCCW1, MCCW2,MCCW+P1, MCCW+P2) may perform transmitting of aggregated digitalimpression information from the MCC to a remote device, such as a remoteserver 925, via a connection to an external communications network. Itwill be understood that, for example, the remote server 925 may beaccessed over the Internet. Remote server 925 may perform remotedisambiguation determining or analyzing of aggregated digital impressionor multidimensional digital impression information including recordedsignal noise and recorded wireless communications information toidentify constituent unique device waveforms in recorded device signalinformation, signal noise and/or conflated device signals, and toidentify constituent device wireless communications properties orwireless constituent device identification information, by a remoteprocessor of the remote server 925 comparing the recorded device signalinformation, signal noise and/or conflated device signals with samplesof known unique device waveforms of known devices and/or devicespreviously or contemporaneously identified at the site, and comparingrecorded wireless communications information with known wirelesscommunications information or properties of known devices or devicetypes to identify constituent device wireless communications propertiesor wireless constituent device unique identification information, whichare stored in memory (not shown) associated with the remote serverand/or stored in a remote database (not shown). It will be understoodthat one suitable database of known devices and device waveforms andidentification information may be, for example, the MIT Project Dilonsignal fingerprint database. Remote server 925 may perform analyzing toidentify devices connected to a subject circuit or capable ofcommunicating over a subject wireless communication channel or wirelessinfrastructure at the site, by identifying unique device waveforms ofknown devices that produce same, or identifying device wirelesscommunications information or properties of known devices, from theremote database. Remote server 925 may transmit identificationinformation of devices from the remote server over a suitablecommunications network to the multifunction communication cubes (MCC'sdesignated MCCW1, MCCW2, MCCW+P1, MCCW+P2). Each of the multifunctioncommunication cubes (MCC's designated MCCW1, MCCW2, MCCW+P1, MCCW+P2)may perform associating of device control pathways, such as commandsignals, with each identified device connected to a subject circuitconnected to a multifunction communication cube (MCC's designated MCCW1,MCCW2, MCCW+P1, MCCW+P2) or visible over a wireless communicationsconnection or channel to a multifunction communication cubes (MCC'sdesignated MCCW1, MCCW2, MCCW+P1, MCCW+P2), by a processor of the same.It will be understood that command signals of devices may be obtainedfrom local memory of the multifunction communication cubes (MCC'sdesignated MCCW1, MCCW2, MCCW+P1, MCCW+P2). Multifunction communicationcubes (MCC's designated MCCW1, MCCW2, MCCW+P1, MCCW+P2) by the local MCCprocessor may generate or transmit command signals or control signalsassociated with identified devices connected to the subject circuit,and/or over a wireless communications connection or channel, to interactwith and control aspects of such identified devices. It will beunderstood that, in some embodiments, command signals or control signalsmay be communicated to such identified devices over a wirelessconnection to an identified device, via a suitable wireless subsystem ofthe multifunction communication cubes (MCC's designated MCCW1, MCCW2,MCCW+P1, MCCW+P2). It will be understood that the first node 906 andsecond node 908 may communicate and share information regarding wiredelectronic devices (PD1, PD2) and wireless devices (WD1, WD2).

FIG. 10 illustrates a system 1000 including network 1004 having a firstnode 1006 and second node 1008. Each of the first node 1006 and secondnode 1008 include a respective single multifunction communication cube(MCC) (1016, 1026) having wireless and wired communications capabilitiesand subsystems. System 1000 may be otherwise identical, or substantiallysimilar, to system 900 illustrated in FIG. 9.

The previous description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the presentinvention. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the generic principles definedherein may be applied to other embodiments without departing from thespirit or scope of the invention. Thus, the present invention is notintended to be limited to the embodiments shown herein but is to beaccorded the widest scope consistent with the principles and novelfeatures disclosed herein.

The benefits and advantages that may be provided by the presentinvention have been described above with regard to specific embodiments.These benefits and advantages, and any elements or limitations that maycause them to occur or to become more pronounced are not to be construedas critical, required, or essential features of any or all of theclaims. As used herein, the terms “comprises,” “comprising,” or anyother variations thereof, are intended to be interpreted asnon-exclusively including the elements or limitations which follow thoseterms. Accordingly, a system, method, or other embodiment that comprisesa set of elements is not limited to only those elements, and may includeother elements not expressly listed or inherent to the claimedembodiment.

While the present invention has been described with reference toparticular embodiments, it should be understood that the embodiments areillustrative and that the scope of the invention is not limited to theseembodiments. Many variations, modifications, additions and improvementsto the embodiments described above are possible. It is contemplated thatthese variations, modifications, additions and improvements fall withinthe scope of the invention as detailed within the following claims.

What is claimed is:
 1. A clamp, comprising: a non-conductive blade; aconductive blade, wherein the conductive blade is offset from thenon-conductive blade; wherein the non-conductive blade is configured tosever a power line and disrupt the power through the power line when theclamp is clamped to the power line; wherein the conductive blade isconfigured to sever the power line into first and second portions andredirect power from the first power line portion while also providingpower from the first power line portion to the second power line portionthrough the conductive blade when the clamp is clamped to the powerline.
 2. The clamp of claim 1, wherein the conductive blade isconfigured to splice into the power line simultaneously with thenon-conductive blade.
 3. The clamp of claim 1, further comprising aninsulated tube, wherein a portion of the non-conductive blade and aportion of the conductive blade are positioned in the insulated tube. 4.The clamp of claim 3, further comprising a contact pad, wherein a firstportion of the contact pad is electrically connected to the conductiveblade, and wherein a second portion of the contact pad is electricallyconnected to the electronic device control apparatus.
 5. The clamp ofclaim 4, wherein the contact pad facilitates flow of current from insideof the insulated tube to an area outside of the insulated tube.
 6. Theclamp of claim 1, wherein the non-conductive blade comprises a piercingsurface configured to splice into the power line.
 7. The clamp of claim1, wherein the conductive blade comprises a piercing surface configuredto splice into the power line.
 8. The clamp of claim 1, wherein theelectronic device control apparatus comprises a processor coupled to theconductive blade.
 9. The clamp of claim 1, wherein the non-conductiveblade is configured to splice first and second conductors of the powerline, and wherein the conductive blade comprises at least two conductiveblades, a first conductive blade being configured to splice the firstconductor, and a second conductive blade being configured to splice thesecond conductor.
 10. A clamp, comprising: a non-conductive blade; afirst conductive blade, wherein the first conductive blade is offsetfrom the non-conductive blade, wherein the first conductive blade iscoupled to an electronic device control apparatus; and a secondconductive blade, wherein the second conductive blade is offset from thenonconductive blade and on an opposite side of the non-conductive bladefrom the first conductive blade, wherein the second conductive blade iscoupled to the electronic device control apparatus; wherein the firstconductive blade and the second conductive blade are configured to severa power line and redirect power from the power line through theelectronic device control apparatus and to an electronic deviceassociated with the power line when the clamp is clamped to the powerline; and wherein the non-conductive blade is configured to sever thepower line and disrupt the power through the power line when the clampis clamped to the power line; thereby providing the power from the powerline to the electronic device control apparatus while continuouslyproviding the power from the power line to the electronic device. 11.The clamp of claim 10, wherein the first conductive blade and the secondconductive blade are configured to splice into the power line when thenonconductive blade servers the power line.
 12. The clamp of claim 10,further comprising an insulated tube, wherein a portion of thenonconductive blade and a portion of the first and second conductiveblades are positioned in the insulated tube.
 13. The clamp of claim 10,further comprising a contact pad electrically connected to at least oneof the first or second conductive blades, and wherein the contact pad iselectrically connected to the electronic device control apparatus. 14.The clamp of claim 10, wherein the non-conductive blade comprises apiercing surface configured to splice into the power line.
 15. The clampof claim 10, wherein at least one of the first or second conductiveblades comprises a piercing surface configured to splice into the powerline.
 16. The clamp of claim 10, wherein the non-conductive blade isconfigured to splice both the first and second conductors of the powerline, wherein the first and second conductive blades are configured tosplice the first conductor, and wherein the clamp further comprises: athird conductive blade, wherein the third conductive blade is offsetfrom the non-conductive blade, wherein the third conductive blade iscoupled to the electronic device control apparatus; and a fourthconductive blade, wherein the fourth conductive blade is offset from thenon-conductive blade and on an opposite side of the non-conductive bladefrom the third conductive blade, wherein the fourth conductive blade iscoupled to the electronic device control apparatus; wherein the thirdconductive blade and the fourth conductive blade are configured tosplice the second conductor.
 17. A method, comprising: splicing into apower line with a non-conductive blade, wherein the non-conductive bladesevers the power line and disrupts power through the power line; andsplicing into the power line with a conductive blade, wherein theconductive blade is offset from the non-conductive blade, and whereinthe conductive blade severs the power line and redirects the power fromthe power line while also providing power back to the power line. 18.The method of claim 17, wherein splicing with the conductive bladecomprises making contact with a conductor in the power line by passingthe conductive blade through insulation of the power line.
 19. Themethod of claim 17, wherein splicing with the non-conductive bladecomprises severing a conductor in the power line through insulation ofthe power line, wherein the conductor is separated into two electricallyseparate conductor sections.
 20. The method of claim 17, wherein thesplicing into the power line with the conductive blade occurssimultaneously with the splicing into the power line with thenon-conductive blade.